\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Without an argument,
\b domainname
\b0 displays the name of the current domain. Only the super-user can set the domainname by giving an argument; this is usually done in the startup script /etc/rc.local. Currently, domains are only used by the yellow pages, to refer collectively to a group of hosts.
CommandArgument
nameofdomain
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The name to set the YP domain to
\b0 takes infile and converts it to a pair of files in dbm(3X) format, namely outfile.pag and outfile.dir. Each line of the input file is converted to a single dbm record. All characters up to the first tab or space form the key, and the rest of the line is the data. If a line ends with , then the data for that record is continued on to the next line. It is left for the clients of the yellow pages to interpret #; makedbm does not itself treat it as a comment character. infile can be -, in which case standard input is read.
\b makedbm
\b0 is meant to be used in generating dbm files for the yellow pages, and it generates a special entry with the key yp_last_modified, which is the date of infile (or the current time, if infile is -).
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Create a special entry with the key yp_input_file
yp_input_file
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The key to create a special entry with
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Create a special entry with the key yp_output_name
yp_output_name
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Create a special entry with the key yp_domain_name
yp_domain_name
1{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Create a special entry with the key yp_master_name. If no master host name is specified, yp_master_name will be set to the local host name
yp_master_name
infile
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The input file to converte
outfile
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The output dbm file
\b0 takes infile and converts it to a pair of files in dbm(3X) format, namely outfile.pag and outfile.dir. Each line of the input file is converted to a single dbm record. All characters up to the first tab or space form the key, and the rest of the line is the data. If a line ends with , then the data for that record is continued on to the next line. It is left for the clients of the yellow pages to interpret #;
\b makedbm
\b0 does not itself treat it as a comment character. infile can be -, in which case standard input is read. makedbm is meant to be used in generating dbm files for the yellow pages, and it generates a special entry with the key yp_last_modified, which is the date of infile (or the current time, if infile is -).
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Undo a dbm file. That is, print out a dbm file one entry per line, with a single space separating keys from values
dbmfilename
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The file to print out the dbm entries to
\b0 is used to take a group(5) file and convert it into a file mapping user names to the group access list for that user. This is used to make the group.byusr NIS map.\
\b mkgrpbyusr
\b0 reads groupfile for input. If no file is specified, then standard input is read.
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\f0\b0\i0\ulnone\ql\fs24\fi0\li0\gray0\fc0\cf0\up0\dn0 Print statistics to stderr regarding internal hash table usage and hit rates
groupfile
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 The group file to read for input
\pard\tx1152\tx2304\tx3456\tx4608\tx5760\tx6912\tx8064\tx9216\tx10368\tx11520\f0\b0\i0\ulnone\fs24\fc0\cf0 The yellow pages (YP) provides a simple network lookup service consisting of databases and processes. The databases are dbm(3) files in a directory tree rooted at /etc/yp. These files are described in ypfiles(5). The processes are /usr/etc/ypserv, the YP database lookup server, and /usr/etc/ypbind, the YP binder. The programmatic interface to YP is described in ypclnt(3N). Administrative tools are described in yppush(8), ypxfr(8), yppoll(8), ypwhich(8), and ypset(8). Tools to see the contents of YP maps are described in ypcat(1), and ypmatch(1). Database generation and maintenance tools are described in ypinit(8), ypmake(8), and makedbm(8). Both ypserv and ypbind are daemon processes typically activated at system startup time from /etc/rc.local. ypserv runs only on YP server machines with a complete YP database. ypbind runs on all machines using YP services, both YP servers and clients. The ypserv daemon's primary function is to look up information in its local database of YP maps. The operations performed by ypserv are defined for the implementor by the YP protocol specification, and for the programmer by the header file <rpcsvc/yp_prot.h>. Communication to and from ypserv is by means of RPC calls. Lookup functions are described in ypclnt(3N), and are supplied as C-callable funtions in /lib/libc. There are four lookup functions, all of which are performed on a specified map within some YP domain: Match, Get_first, Get_next, and Get_all. The Match operation takes a key, and returns the associated value. The Get_first operation returns the first key-value pair from the map, and Get_next can be used to enumerate the remainder. Get_all ships the entire map to the requester as the response to a single RPC request. Two other functions supply information about the map, rather than map entries: Get_order_number, and Get_master_name. In fact, both order number and master name exist in the map as key-value pairs, but the server will not return either through the normal lookup functions. (If you examine the map with makedbm(8), however, they will be visible.) Other functions are used within the YP subsystem itself, and are not of general interest to YP clients. They include Do_you_serve_this_domain?, Transfer_map, and Reinitialize_internal_state. The function of ypbind is to remember information that lets client processes on a single node communicate with some ypserv process. ypbind must run on every machine which has YP client processes; ypserv may or may not be running on the same node, but must be running somewhere on the network. The information ypbind remembers is called a binding the association of a domain name with the internet address of the YP server, and the port on that host at which the ypserv process is listening for service requests. The process of binding is driven by client requests. As a request for an unbound domain comes in, the ypbind process broadcasts on the net trying to find a ypserv process that serves maps within that domain. Since the binding is established by broadcasting, there must be at least one ypserv process on every net. Once a domain is bound by a particular ypbind, that same binding is given to every client process on the node. The ypbind process on the local node or a remote node may be queried for the binding of a particular domain by using the ypwhich(1) command. Bindings are verified before they are given out to a client process. If ypbind is unable to speak to the ypserv process it's bound to, it marks the domain as unbound, tells the client process that the domain is unbound, and tries to bind the domain once again. Requests received for an unbound domain will fail immediately. In general, a bound domain is marked as unbound when the node running ypserv crashes or gets overloaded. In such a case, ypbind will to bind any YP server (typically one that is less-heavily loaded) available on the net. ypbind also accepts requests to set its binding for a particular domain. The request is usually generated by the YP subsystem itself. ypset(8) is a command to access the Set_domain facility. It is for unsnarling messes, not for casual use.
\b0 prints out values in a yellow pages (YP) map specified by mname, which may be either a mapname or a map nickname. Since ypcat uses the YP network services, no YP server is specified.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Display the keys for those maps in which the values are null or the key is not part of the value. (None of the maps derived from files that have an ASCII version in /etc fall into this class.)
[{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Inhibit translation of mname to mapname. For example, ypcat -t passwd will fail because there is no map named passwd, whereas ypcat passwd will be translated to ypcat passwd.byname
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Specify a domain other that the default domain. The default domain is returned by domainname
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The domain to be used
6{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Display the map nickname table. This lists the nicknames (mnames) the command knows of, and indicates the mapname associated with each nickname
\b0 sets up a yellow pages database on a YP server. It can be used to set up a master or a slave server. You must be the superuser to run it. It asks a few, self-explanatory questions, and reports success or failure to the terminal. It sets up a master server using the simple model in which that server is master to all maps in the data base. This is the way to bootstrap the YP system; later if you want you can change the association of maps to masters. All databases are built from scratch, either from information available to the program at runtime, or from the ASCII data base files in /etc. These files are listed below under FILES . All such files should be in their "traditional" form, rather than the abbreviated form used on client machines. A YP database on a slave server is set up by copying an existing database from a running server. The master_name argument should be the hostname of YP server (either the master server for all the maps, or a server on which the data base is up-to-date and stable). Refer to ypfiles(5) and ypserv(8) for an overview of the yellow pages.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Indicates that the local host is to be the YP master
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 The file called Makefile in /usr/etc/yp is used by make to build the yellow pages database. With no arguments, make creates dbm databases for any YP maps that are out-of-date, and then executes yppush to notify slave databases that there has been a change. If you supply a map on the command line, make will update that map only. Typing make passwd will create and yppush the password database (assuming it is out of date). Likewise, make hosts and make networks will create and yppush the host and network files, /etc/hosts and /etc/networks. There are three special variables used by make: DIR, which gives the directory of the source files; NOPUSH, which when non-null inhibits doing a yppush of the new database files; and DOM, used to construct a domain other than the master's default domain. The default for DIR is /etc, and the default for NOPUSH is the null string. Refer to ypfiles(5) and ypserv(8) for an overview of the yellow pages.
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The map to update
\b0 prints the values associated with one or more keys from the yellow pages (YP) map specified by a mname, which may be either a mapname or an map nickname. Multiple keys can be specified; the same map will be searched for all . The keys must be exact values insofar as capitalization and length are concerned. No pattern matching is available. If a key is not matched, a diagnostic message is produced.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Specify a domain other that the default domain
domain
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Before printing the value of a key, print the key itself, followed by a colon (':'). This is useful only if the keys are not duplicated in the values, or you've specified so many keys that the output could be confusing
t{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Inhibit translation of nickname to mapname. For example, ypmatch -t zippy passwd will fail because there is no map named passwd, while ypmatch zippy passwd will be translated to ypmatch zippy passwd.byname
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The key(s) to print the value(s) for
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The YP map to print the values used
\b0 changes (or installs) a network password associated with the user name (your own name by default) in the yellow pages. The yellow pages password may be different from the one on your own machine. Yppasswd prompts for the old yellow pages password, and then for the new one. You must type in the old password correctly for the change to take effect. The new password must be typed twice, to forestall mistakes. New passwords must be at least four characters long, if they use a sufficiently rich alphabet, and at least six characters long if monocase. These rules are relaxed if you are insistent enough. Only the owner of the name or the superuser may change a password; in either case you must prove you know the old password. The yellow-pages password daemon, yppasswdd(8C) must be running on your YP server in order for the new password to take effect.
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The user name to set the YP password for
\b0 asks a ypserv process what the order number is, and which host is the master YP server for the named map. If the server is a v.1 YP protocol server, yppoll uses the older protocol to communciate with it. In this case, it also uses the older diagnostic messages in case of failure.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Ask the ypserv process at host about the map parameters. If host isn't specified, the YP server for the local host is used. That is, the default host is the one returned by ypwhich(8)
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The host running the ypserv process to query
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Use domain instead of the default domain
mapname
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The map to ask for the master YP server
\b0 copies a new version of a Yellow Pages (YP) map from the master YP server to the slave YP servers. It is normally run only on the master YP server by the Makefile in /usr/etc/yp/ after the master databases are changed. It first constructs a list of YP server hosts by reading the YP map ypservers within the domain. Keys within the map ypservers are the ASCII names of the machines on which the YP servers run. A ``transfer map'' request is sent to the YP server at each host, along with the information needed by the transfer agent (the program which actually moves the map) to call back the yppush . When the attempt has completed (successfully or not), and the transfer agent has sent yppush a status message, the results may be printed to stdout. Messages are also printed when a transfer is not possible; for instance when the request message is undeliverable, or when the timeout period on responses has expired. Refer to ypfiles(5) and ypserv(8) for an overview of the yellow pages.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Specify a domain
>{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Verbose. This causes messages to be printed when each server is called, and for each response. If this flag is omitted, only error messages are printed
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The name of the map to use
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 The yellow pages (YP) provides a simple network lookup service consisting of databases and processes. The databases are dbm(3) files in a directory tree rooted at /etc/yp. These files are described in ypfiles(5). The processes are /usr/etc/ypserv, the YP database lookup server, and /usr/etc/ypbind, the YP binder. The programmatic interface to YP is described in ypclnt(3N). Administrative tools are described in yppush(8), ypxfr(8), yppoll(8), ypwhich(8), and ypset(8). Tools to see the contents of YP maps are described in ypcat(1), and ypmatch(1). Database generation and maintenance tools are described in ypinit(8), ypmake(8), and makedbm(8). Both ypserv and ypbind are daemon processes typically activated at system startup time from /etc/rc.local. ypserv runs only on YP server machines with a complete YP database. ypbind runs on all machines using YP services, both YP servers and clients. The ypserv daemon's primary function is to look up information in its local database of YP maps. The operations performed by ypserv are defined for the implementor by the YP protocol specification, and for the programmer by the header file <rpcsvc/yp_prot.h>. Communication to and from ypserv is by means of RPC calls. Lookup functions are described in ypclnt(3N), and are supplied as C-callable funtions in /lib/libc. There are four lookup functions, all of which are performed on a specified map within some YP domain: Match, Get_first, Get_next, and Get_all. The Match operation takes a key, and returns the associated value. The Get_first operation returns the first key-value pair from the map, and Get_next can be used to enumerate the remainder. Get_all ships the entire map to the requester as the response to a single RPC request. Two other functions supply information about the map, rather than map entries: Get_order_number, and Get_master_name. In fact, both order number and master name exist in the map as key-value pairs, but the server will not return either through the normal lookup functions. (If you examine the map with makedbm(8), however, they will be visible.) Other functions are used within the YP subsystem itself, and are not of general interest to YP clients. They include Do_you_serve_this_domain?, Transfer_map, and Reinitialize_internal_state. The function of ypbind is to remember information that lets client processes on a single node communicate with some ypserv process. ypbind must run on every machine which has YP client processes; ypserv may or may not be running on the same node, but must be running somewhere on the network. The information ypbind remembers is called a binding the association of a domain name with the internet address of the YP server, and the port on that host at which the ypserv process is listening for service requests. The process of binding is driven by client requests. As a request for an unbound domain comes in, the ypbind process broadcasts on the net trying to find a ypserv process that serves maps within that domain. Since the binding is established by broadcasting, there must be at least one ypserv process on every net. Once a domain is bound by a particular ypbind, that same binding is given to every client process on the node. The ypbind process on the local node or a remote node may be queried for the binding of a particular domain by using the ypwhich(1) command. Bindings are verified before they are given out to a client process. If ypbind is unable to speak to the ypserv process it's bound to, it marks the domain as unbound, tells the client process that the domain is unbound, and tries to bind the domain once again. Requests received for an unbound domain will fail immediately. In general, a bound domain is marked as unbound when the node running ypserv crashes or gets overloaded. In such a case, ypbind will to bind any YP server (typically one that is less-heavily loaded) available on the net. ypbind also accepts requests to set its binding for a particular domain. The request is usually generated by the YP subsystem itself. ypset(8) is a command to access the Set_domain facility. It is for unsnarling messes, not for casual use.
\b0 tells ypbind to get YP services for the specified domain from the ypserv process running on server. If server is down, or isn't running ypserv, this is not discovered until a YP client process tries to get a binding for the domain. At this point, the binding set by ypset will be tested by ypbind. If the binding is invalid, ypbind will attempt to rebind for the same domain. ypset is useful for binding a client node which is not on a broadcast net, or is on a broadcast net which isn't running a YP server host. It also is useful for debugging YP client applications, for instance where a YP map only exists at a single YP server host. In cases where several hosts on the local net are supplying YP services, it is possible for ypbind to rebind to another host even while you attempt to find out if the ypset operation succeeded. That is, you can type "ypset host1", and then "ypwhich", which replies: "host2", which can be confusing. This is a function of the YP subsystem's attempt to load-balance among the available YP servers, and occurs when host1 does not respond to ypbind because it is not running ypserv (or is overloaded), and host2, running ypserv, gets the binding. server indicates the YP server to bind to, and can be specified as a name or an IP address. If specified as a name, ypset will attempt to use YP services to resolve the name to an IP address. This will work only if the node has a current valid binding for the domain in question. In most cases, server should be specified as an IP address. Refer to ypfiles(5) and ypserv(8) for an overview of the yellow pages.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Bind server for the (old) v.1 YP protocol
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Bind server for the (current) v.2 YP protocol
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Set ypbind's binding on host, instead of locally. host can be specified as a name or as an IP address
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The host to set ypbind's binding on
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 Use domain, instead of the default domain
server
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The server to the YP services from
\b0 tells which YP server supplies yellow pages services to a YP client, or which is the master for a map. If invoked without arguments, it gives the YP server for the local machine. If hostname is specified, that machine is queried to find out which YP master it is using. Refer to ypfiles(5) and ypserv(8) for an overview of the yellow pages.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Inhibit nickname translation; useful if there is a mapname identical to a nickname
W{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Find the master YP server for a map. No hostname can be specified with -m. mname can be a mapname, or a nickname for a map. When mname is omitted, produce a list available maps
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The map name or map nickname to use
hostname
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The host queried to find out which YP master it is using
\b0 moves a YP map to the local host by making use of normal YP services. It creates a temporary map in the directory /etc/yp/domain (which must already exist), fills it by enumerating the map's entries, fetches the map parameters (master and order number), and loads them. It then deletes any old versions of the map and moves the temporary map to the real mapname. If ypxfr is run interactively, it writes its output to the terminal. However, if it is invoked without a controlling terminal, and if the log file /etc/yp/ypxfr.log exists, it will append all its output to that file. Since ypxfr is most often run from /usr/lib/crontab, or by ypserv, you can use the log file to retain a record of what was attempted, and what the results were. For consistency between servers, ypxfr should be run periodically for every map in the YP data base. Different maps change at different rates: the services.byname map may not change for months at a time, for instance, and may therefore be checked only once a day in the wee hours. You may know that mail.aliases or hosts.byname changes several times per day. In such a case, you may want to check hourly for updates. A crontab(5) entry can be used to perform periodic updates automatically. Rather than having a separate crontab entry for each map, you can group comands to update several maps in a shell script. Examples (mnemonically named) are in /etc/yp: ypxfr_1perday.sh, ypxfr_2perday.sh, and ypxfr_1perhour.sh. They can serve as reasonable first cuts. Refer to ypfiles(5) and ypserv(8) for an overview of the yellow pages.
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Force the transfer to occur even if the version at the master is not more recent than the local version
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Don't send a "Clear current map" request to the local ypserv process. Use this flag if ypserv is not running locally at the time you are running ypxfr. Otherwise, ypxfr will complain that it can't talk to the local ypserv, and the transfer will fail
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Get the map from host, regardless of what the map says the master is. If host is not specified, ypxfr will ask the YP service for the name of the master, and try to get the map from there. host may be a name or an internet address in the form a.b.c.d
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The host to get the map from
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 Specify a domain other than the default domain.
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx533\tx1067\tx1601\tx2135\tx2668\tx3202\tx3736\tx4270\tx4803\tx5337\f0\b0\i0\ulnone\fs24\fc0\cf0 This option is only for use by ypserv. When ypserv invokes ypxfr, it specifies that ypxfr should call back a yppush process at the host with IP address ipaddr, registered as program number prog, listening on port port, and waiting for a response to transaction tid
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The transaction id
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The program number
ipadd
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The IP address
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The port to listen on
{\rtf0\ansi{\fonttbl\f0\fmodern Courier;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 The name of the map to move
(.txt)